Scrum: Step-by-Step Agile Guide to Scrum (Scrum Roles, Scrum Artifacts, Sprint Cycle, User Stories, Scrum Planning) by Jason Bennett & Jennifer Bowen

Author:Jason Bennett & Jennifer Bowen [Bennett, Jason]
Language: eng
Format: azw3
Published: 2018-11-11T16:00:00+00:00

Chapter Four: User Stories

In Scrum, development tasks are not merely technical-sounding to-do lists. User stories are employed to explain users’ system requirements, functional and non-functional end-uses, and other expectations from the product that is being developed.

Scrum gives a lot of importance to user stories primarily because through this process, the development team focuses on the user and his or her needs rather than treating the product development merely as a technical process.

User stories shift the focus of the technical development team from creating software codes mindlessly to solving customer problems with their technical skills.

User stories are accurate representations of user desires and needs. The success of any product development depends on the understanding of user needs by the team. User stories are a great way to achieve this precise and unambiguous understanding of user needs by the developers.

Typically in Scrum, the Product Backlog is a collection of all user stories. Of course, the product owner does not merely dump the user stories into the Product Backlog artifact but orders and prioritizes them to help the development team pick up the most important user stories to be included in the next Sprint.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.